home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-12-18 | 79.2 KB | 1,940 lines |
- #define FOO_VER 1
- //====================================================================== System/Version Stuff
-
- #define TRS_SAVE_NAME 2
- //MORTIMER.CFG
-
- #define TRS_TITLE 5
- //^f01Mortimer^c015^f02$^f00
- //^f02^c007And the Riddles of the Medallion$
- //
- //^c008Version 0.8 18-Dec-95, ~1995 Lucasfilm Ltd.
- //^f00Portions (c)1993-1995 SciTech Software
-
- #define TRS_SYSTEM_OKAY 6
- //^f02Okay
-
- #define TRS_SYSTEM_O 7
- //o
-
- #define TRS_SYSTEM_CANCEL 8
- //^f02Cancel
-
- #define TRS_SYSTEM_C 9
- //c
-
-
- #define FOO_AUTO 1
- //====================================================================== Auto-detect text
-
- #define TRS_AUTO_REQUEST 10
- //^f02Auto-detect sound, CPU, and CD settings?^f00
- //
- //^c011^f02Settings file %s\%s will be created.^c000^f00
- //
- //^c011Note: Rarely, autodetect may lockup due to a system conflict.
- //If this occurs, restart the game and perform the setup manually.
-
- #define TRS_AUTOSAVE_REQUEST 11
- //^c011^f02Sound Card: %s
- //Sound Settings: %s
- //^c000Save configuration to %s\%s ?
-
- #define TRS_AUTO_ABORT 12
- //^f02Abort
- #define TRS_AUTO_A 13
- //a
-
- #define TRS_AUTO_TEST_SOUND 14
- //^f02Testing Sound Card
- #define TRS_AUTO_TEST_CPU 15
- //^f02Testing CPU
- #define TRS_AUTO_TEST_CD 16
- //^f02Testing CD Drive
-
- #define TRS_HIRES_REQUEST 17
- //^c011^f02You may optionally run the game in high resolution.
- //
- //Do you wish to set the default resolution to High-Res?
-
- #define TRS_BOOT_REQUEST 18
- //You are currently running under a Windows 95 DOS box or in MSDOS Mode, where you may
- //not have enough low memory to run the bootdisk maker from within this launcher.
- //
- //Run the bootdisk maker directly from the Windows 95 Desktop. Do this by first exiting
- //this launcher and opening up the SUPPORT folder on the Mortimer CD. Double-click
- //on the BOOTDISK icon and follow the on-screen instructions.
-
- #define FOO_MAIN 1
- //====================================================================== Main Menu Titles
-
- #define TRS_MENU0 19
- //^f01 Launcher Main Menu
-
- #define TRS_MENU_KEYS 20
- //psmtibq
-
- #define TRS_MENU1 21
- //^f02Play Mortimer
-
- #define TRS_MENU2 22
- //^f02Setup
-
- #define TRS_MENU3 23
- //^f02Manual
-
- #define TRS_MENU5 25
- //^f02Troubleshooting Guide
-
- #define TRS_MENU6 26
- //^f02Show System Info
-
- #define TRS_MENU7 27
- //^f02Make Boot Disk
-
- #define TRS_MENU8 28
- //^f02Quit Mortimer
-
-
- #define FOO_SET 1
- //====================================================================== Settings Menu Titles
-
- #define TRS_SET_KEYS 34
- //astibdkrvc
-
- #define TRS_SET_REQUEST 35
- //^f01Current Settings
-
- #define TRS_SET_AUTO 36
- //^f02Auto-Detect
-
- #define TRS_SET_CARD 37
- //^f02Sound Card: %s
-
- #define TRS_SET_TEST 38
- //^f02Test Sound
-
- #define TRS_SET_IRQ 39
- //^f02IRQ: %hd
-
- #define TRS_SET_BASE 40
- //^f02Base: %hx
-
- #define TRS_SET_DMA 41
- //^f02DMA: %hd
-
- #define TRS_SET_IRQ_UNUSED 42
- //^f02IRQ: Unused
-
- #define TRS_SET_BASE_UNUSED 43
- //^f02Base: Unused
-
- #define TRS_SET_DMA_UNUSED 44
- //^f02DMA: Unused
-
- #define TRS_SET_STEREO1 47
- //^f02Speaker Orientation: Normal
-
- #define TRS_SET_STEREO2 48
- //^f02Speaker Orientation: Reversed
-
- #define TRS_SET_RESOLUTION 49
- //^f02Res: Low (320x200)
-
- #define TRS_SET_RESOLUTION3 51
- //^f02Res: High (640x400)
-
- #define TRS_SET_ADVANCED 52
- //^f02ADVANCED SETTINGS
-
- #define TRS_SET_CONTINUE 53
- //^f02CONTINUE
-
-
- #define FOO_ADV 1
- //====================================================================== Advanced Menu Titles
-
-
- #define TRS_ADVANCED_REQUEST 55
- //^f01Advanced Settings
-
- #define TRS_ADVANCED_KEYS 56
- //tfsvrc
-
- #define TRS_ADVANCED_TIMER 57
- //^f02Task Switcher: %hd Hz Int
-
- #define TRS_ADVANCED_FRAME 58
- //^f02Frame Rate: %hd Fps
-
- #define TRS_ADVANCED_SAMPLE 59
- //^f02Sample Rate: %ld Hz
-
- #define TRS_ADVANCED_CONTINUE 60
- //^f02CONTINUE
-
- #define TRS_ADVANCED_SEQUENTIAL 61
- //^f02Task Switcher: Cooperative
-
- #define TRS_ADVANCED_VESA_NORMAL 62
- //^f02VESA Video Driver: Auto
-
- #define TRS_ADVANCED_VESA_FORCED 63
- //^f02VESA Video Driver: Force UNIVBE
-
- #define TRS_ADVANCED_RESET 64
- //^f02Reset to Defaults
-
- #define FOO_CARD 1
- //====================================================================== Sound Card Titles
-
- #define TRS_CARD_REQUEST 69
- //^f01Please Select a Sound Card
-
- #define TRS_CARD_KEYS 70
- //nebpsrauq
-
- #define TRS_SOUNDCARD1 71
- //^f02None
-
- #define TRS_SOUNDCARD2 72
- //^f02Early Sound Blaster
-
- #define TRS_SOUNDCARD3 73
- //^f02Standard Sound Blaster
-
- #define TRS_SOUNDCARD4 74
- //^f02Sound Blaster Pro
-
- #define TRS_SOUNDCARD5 75
- //^f02Sound Blaster 16 / AWE32 / SB32
-
- #define TRS_SOUNDCARD6 76
- //^f02Pro AudioSpectrum 16
-
- #define TRS_SOUNDCARD7 77
- //^f02Aria
-
- #define TRS_SOUNDCARD8 78
- //^f02UltraSound
-
- #define TRS_SOUNDCARD9 79
- //^f02Ensoniq
-
-
- #define FOO_MISC 1
- //====================================================================== Misc Settings Titles
-
- #define TRS_IRQ_REQUEST 97
- //^f01Set IRQ Channel
-
- #define TRS_IRQ_VALUE 98
- //^f02IRQ Channel:
-
- #define TRS_BASE_REQUEST 102
- //^f01Set Base Address
-
- #define TRS_DMA_REQUEST 104
- //^f01Set DMA Channel
-
- #define TRS_DMA_VALUE 105
- //^f02DMA Channel:
-
- #define TRS_OTHER_VALUE 109
- //^f02Other...
- #define TRS_OTHER_KEY 110
- //o
-
-
- #define TRS_VOLUME_REQUEST 117
- //^f01Set Test Volume Level
-
- #define TRS_VOLUME_VALUE 118
- //^f02Volume Level
-
- #define TRS_TIMERRATE_REQUEST 120
- //^f01Adjust Task Switcher
-
- #define TRS_TIMERRATE_VALUE 121
- //^f02Interrupt Timer Rate
-
- #define TRS_SEQUENTIAL_VALUE 122
- //^f02Multitasking Method Preemptive Cooperative
-
- #define TRS_RESOLUTION_REQUEST 123
- //^f01Adjust Resolution
-
- #define TRS_RESOLUTION_VALUE 124
- //^f02Resolution: Low High (VESA)
-
- #define TRS_FRAMERATE_REQUEST 125
- //^f01Adjust Frame Rate
-
- #define TRS_FRAMERATE_VALUE 126
- //^f02Frame Rate
-
- #define TRS_SAMPLERATE_REQUEST 130
- //^f01Adjust Sample Rate
-
- #define TRS_SAMPLERATE_VALUE 131
- //^f02Sample Rate
-
-
- #define FOO_SYS 1
- //====================================================================== System Text
-
- #define TRS_SAVE_TITLE 135
- //^f01System Request
-
- #define TRS_SAVE_YES 136
- //^f01Yes
-
- #define TRS_SAVE_NO 137
- //^f01No
-
- #define TRS_SAVE_Y 138
- //y
-
- #define TRS_SAVE_N 139
- //n
-
- #define TRS_SAVE_REQUEST 140
- //^f02Save configuration to %s\%s ?
-
- #define TRS_SYSTEM_ERROR 141
- //^f01Error Message
-
- #define TRS_UVCONFIG_REQUEST 142
- //Your video card is either not configured for VESA modes
- //or UNIVBE-forcing is active.
- //
- //Continue by configuring universal video driver UNIVBE?
- //
- //(File %s will be created )
- //Note: This may crash if your video card is not supported.
-
- #define TRS_UVCONFIG_FAIL 143
- //UNIVBE Failed to create %s
- //Your video card may not be supported by UNIVBE or may require
- //a VESA TSR program in order to run.
- //Please consult your video card manufacturer.
- //
-
- #define TRS_UNIVBE_FAIL 144
- //UNIVBE Failed to initialize using config file
- //%s. Driver may be incorrect for video card or
- //you may be missing a VESA TSR program to run.
- //(Please consult your video card documentation.)
- //
- //Re-run UNIVBE configuration program?
-
- #define TRS_LORES_CONTINUE 145
- //Continue to run game in low resolution?
-
-
- #define FOO_INFO 1
- //====================================================================== SysInfo Text
-
- #define TRS_SYSINFO_TEST 198
- //^f02Testing...
-
- #define TRS_SYSINFO_DATA 199
- //4500000 500000 40 33 225000 25000 18 17 ; mem_min, mem_inc, proc_min, proc_inc, cd_min, cd_inc, video_min, video_inc
-
- #define TRS_SYSINFO_TITLE_V 200
- //^f01Video
-
- #define TRS_SYSINFO_TITLE_M 201
- //^f01Memory
-
- #define TRS_SYSINFO_TITLE_P 202
- //^f01Processor
-
- #define TRS_SYSINFO_TITLE_C 203
- //^f01CD-ROM Drive
-
- #define TRS_SYSINFO_BODY_M1 205
- //^c001^f02Protect Mode Memory^c000^f00
- //
- // Maximum Available: %6ldk
- // Total Free: %6ldk
- // Largest Free Block: %6ldk
-
- #define TRS_SYSINFO_BODY_M2 206
- //^c001EMS Memory^c000
- //
- // There is an EMS memory manager present.
- // EMS Available %6ldk
- // EMS Allocated %6ldk
-
- #define TRS_SYSINFO_BODY_M3 207
- //^c001^f02EMS Memory^c000^f00
- //
- // There is no memory manager present.
-
- #define TRS_SYSINFO_TEXT_M_Y 208
- //^c011
- // You have enough memory to run Mortimer properly. You do not have an EMS memory
- // manager installed, which is correct, as Mortimer cannot use EMS memory. In fact,
- // some memory managers actually interfere with Mortimer, slowing the game down or
- // causing intermittent crash bugs.
-
- #define TRS_SYSINFO_TEXT_M_N 209
- //^c011
- // You may not have enough protected mode memory to run Mortimer properly. Mortimer
- // requires at least 6 Megabytes of protected mode memory to run, but does not use base memory
- // (memory below 640k) or EMS memory. Thus, installing a memory manager will not help. In fact,
- // some memory managers actually interfere with Mortimer, causing bugs or slow-downs.
-
- #define TRS_SYSINFO_TEXT_M_EY 210
- //^c011
- // You have enough memory to run Mortimer properly, but you also have an EMS memory manager
- // installed. Some memory managers actually interfere with the program, slowing the game down
- // or causing intermittent crash bugs. You may wish to run off a boot disk if you encounter
- // problems running the game.
-
- #define TRS_SYSINFO_TEXT_M_EN 211
- //^c011
- // You may not have enough protected mode memory to run Mortimer properly. In addition, you
- // also have an EMS memory manager installed. Some memory managers interfere with Mortimer,
- // robbing-away protected mode memory, slowing the game down, or causing intermittent crash
- // bugs. You should make a boot disk and reboot off it before running the game.
-
- #define TRS_SYSINFO_BODY_P 212
- // Type: %s
- // Approx Speed: %ld MHz
- //
- // Dos Version: %d.%d
- // Boot Drive: %c:
-
- #define TRS_SYSINFO_TEXT_P_Y 213
- //^c011
- // A test of your CPUs
- // approximate speed shows
- // it to be fast enough to
- // run the game adequately.
- //
- // A 50Mhz '486 or better is
- // recommended.
-
- #define TRS_SYSINFO_TEXT_P_N 214
- //^c011
- // A test of your CPUs
- // speed shows it may be too
- // slow to run the game
- // adequately, depending on
- // your other components.
- //
- // A 50Mhz '486 or better is
- // recommended.
-
- #define TRS_SYSINFO_BODY_C 215
- // MSCDEX version: %hd.%hd
- // CD Drive: %c:
- // Speed w/ 40%% cpu: %ld Kps
- // Speed w/ 50%% cpu: %ld Kps
- // Speed w/ 60%% cpu: %ld Kps
-
- #define TRS_SYSINFO_TEXT_C_Y 216
- //^c011
- // Your cd drive appears to
- // run adequately at a %hd%%
- // CPU Usage. MPC-Level 2
- // allows 60%% maximum. Mortimer
- // requires a minimum sustained
- // transfer rate of 225 kps.
-
- #define TRS_SYSINFO_TEXT_C_N 217
- //^c011
- // Your cd drive appears to be
- // too slow when run at a 40-60%%
- // CPU Usage. The MPC-Level 2
- // standard allows at most 60%%.
- //
- // Mortimer requires a rate of
- // 225 kps. To accomplish this,
- // you may experience a slower
- // frame rate.
-
- #define TRS_SYSINFO_TEXT_C_Z 218
- //^c011
- // SysInfo was not able to test
- // your CD drive successfully.
- // Either the benchmark CD/File
- // is missing or damaged, or
- // your cd drive cannot operate
- // at a 40-60% cpu usage level.
- // MPC-Level 2 requires 60%.
-
- #define TRS_SYSINFO_BODY_V 219
- // Driver: %s
- // Make: %s
- // Modes: %s
- // Speed: %ld Kps (%ld fps)
-
- #define TRS_SYSINFO_TEXT_V_Y 220
- //^c011
- // Your video card seems
- // fast enough to run the
- // game adequately.
- //
- // A slow video card
- // can drastically affect
- // performance, especially
- // on slower machines.
-
- #define TRS_SYSINFO_TEXT_V_N 221
- //^c011
- // Your video card appears
- // to be rather slow.
- //
- // A slow video card
- // can drastically affect
- // performance, especially
- // on slower machines.
-
- #define TRS_SYSINFO_OKAY 225
- //^f01Exit
- #define TRS_SYSINFO_OKAY_KEY 226
- //x
- #define TRS_SYSINFO_HELP 227
- //^f01Help
- #define TRS_SYSINFO_HELP_KEY 228
- //h
-
-
- #define FOO_CON 1
- //======================================================================
- //
- // Control Page for Manual
- //
- //======================================================================
-
- #define TRS_MANUAL_CONTROL 251
- // 20 ; number of pages
- // 0 259 10 ; page 0, text 259, 11 buttons
- // -1 x (^f01Exit) 10 -30 100 20
- // 1 n (^f01Next) -110 -30 100 20 ; next
- // 1 i (^f02Intro...) 400 -257 100 20
- // 2 s (^f02Setup...) 400 -237 100 20
- // 4 g (^f02Start Game...) 400 -217 100 20
- // 6 c (^f02Controls...) 400 -197 100 20
- // 8 p (^f02Game Play...) 400 -177 100 20
- // 9 o (^f02Options...) 400 -157 100 20
- // 12 y (^f02SysInfo...) 400 -117 100 20
- // 16 f (^f02Files...) 400 -97 100 20
- // 1 260 4 ; INTRO
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 0 p (^f01Prev) -215 -30 100 20
- // 15 n (^f01Next) -110 -30 100 20
- // 2 262 4 ; SETUP 1
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 15 p (^f01Prev) -215 -30 100 20
- // 3 n (^f01Next) -110 -30 100 20
- // 3 263 4 ; SETUP 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 2 p (^f01Prev) -215 -30 100 20
- // 4 n (^f01Next) -110 -30 100 20
- // 4 264 4 ; START 1
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 3 p (^f01Prev) -215 -30 100 20
- // 5 n (^f01Next) -110 -30 100 20
- // 5 265 4 ; START 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 4 p (^f01Prev) -215 -30 100 20
- // 6 n (^f01Next) -110 -30 100 20
- // 6 266 4 ; CONTROL 1
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 5 p (^f01Prev) -215 -30 100 20
- // 7 n (^f01Next) -110 -30 100 20
- // 7 267 4 ; CONTROL 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 6 p (^f01Prev) -215 -30 100 20
- // 8 n (^f01Next) -110 -30 100 20
- // 8 268 4 ; PLAY
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 18 n (^f01Next) -110 -30 100 20
- // 9 269 4 ; OPTIONS 1
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 18 p (^f01Prev) -215 -30 100 20
- // 12 n (^f01Next) -110 -30 100 20
- // 10 270 1 ; UNUSED
- // -1 x (^f01Exit) 10 -30 100 20
- // 11 271 1 ; UNUSED
- // -1 x (^f01Exit) 10 -30 100 20
- // 12 276 4 ; SYSINFO 1
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 9 p (^f01Prev) -215 -30 100 20
- // 13 n (^f01Next) -110 -30 100 20
- // 13 277 4 ; SYSINFO 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 12 p (^f01Prev) -215 -30 100 20
- // 14 n (^f01Next) -110 -30 100 20
- // 14 278 4 ; SYSINFO 3
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 13 p (^f01Prev) -215 -30 100 20
- // 16 n (^f01Next) -110 -30 100 20
- // 15 261 5 ; INTRO 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 1 p (^f01Prev) -215 -30 100 20
- // 2 n (^f01Next) -110 -30 100 20
- // 17 m (^f02Making a Boot Disk...) 40 -70 200 20
- // 16 274 4 ; FILES
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 19 i (^f02How to Custom Install...) 40 -75 200 20
- // 17 273 3 ; MAKING A BOOT DISK
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 15 p (^f01Prev) -215 -30 100 20
- // 18 272 4 ; GAME PLAY CONTINUED
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 8 p (^f01Prev) -215 -30 100 20
- // 9 n (^f01Next) -110 -30 100 20
- // 19 275 3 ; FILE CUSTOM
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 16 p (^f01Prev) -215 -30 100 20
-
- #define FOO_I_CON 1
- //======================================================================
- //
- // Control Page for Info Help
- //
- //======================================================================
-
- #define TRS_INFOHELP_CONTROL 253
- // 3 ; number of pages
- // 0 276 2 ; page, text #, buttons
- // -1 x (^f01Exit) 10 -30 100 20 ; jump vector, hot-key, button text
- // 1 n (^f01Next) -110 -30 100 20
- // 1 277 3
- // -1 x (^f01Exit) 10 -30 100 20
- // 2 n (^f01Next) -110 -30 100 20
- // 0 p (^f01Prev) -215 -30 100 20
- // 2 278 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 1 p (^f01Prev) -215 -30 100 20
-
- #define FOO_T_CON 1
- //======================================================================
- //
- // Control Page for Troubleshooting guide
- //
- //======================================================================
-
- #define TRS_TROUBLE_CONTROL 254
- // 30 ; number of pages
- // 0 300 10 ; HOME PAGE
- // -1 x (^f01Exit) 10 -30 100 20
- // 1 n (^f01Next) -110 -30 100 20
- // 1 c (^f02Crashes...) 380 -205 120 20
- // 4 j (^f02Joysticks...) 380 -185 120 20
- // 5 m (^f02Memory...) 380 -165 120 20
- // 6 a (^f02Audio...) 380 -145 120 20
- // 12 v (^f02Video...) 380 -125 120 20
- // 13 s (^f02Speed...) 380 -105 120 20
- // 22 e (^f02Error Messages...) 380 -85 120 20
- // 24 t (^f02Tech Support...) 380 -65 120 20
- // 1 301 5 ; CRASHES
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 0 p (^f01Prev) -215 -30 100 20
- // 2 n (^f01Next) -110 -30 100 20
- // 3 m (^f02Making a Boot Disk...) 40 -65 280 20
- // 2 302 7 ; CRASHES2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 1 p (^f01Prev) -215 -30 100 20
- // 28 n (^f01Next) -110 -30 100 20
- // -2 i (^f02Install 1.97 Now) 50 -175 100 20 (LAUNCH\DO_COPY DRIVERS\4GW197.EXE C:\MORTIMER\DOS4GW.EXE)
- // -2 n (^f02Install 1.95 Now) 170 -175 100 20 (LAUNCH\DO_COPY DRIVERS\4GW195.EXE C:\MORTIMER\DOS4GW.EXE)
- // -2 s (^f02Install 1.92 Now) 290 -175 100 20 (LAUNCH\DO_COPY DRIVERS\4GW192.EXE C:\MORTIMER\DOS4GW.EXE)
- // 3 273 3 ; MAKING A BOOT DISK
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 1 p (^f01Prev) -215 -30 100 20
- // 4 305 4 ; JOYSTICK
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 2 p (^f01Prev) -215 -30 100 20
- // 5 n (^f01Next) -110 -30 100 20
- // 5 307 5 ; MEMORY
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 4 p (^f01Prev) -215 -30 100 20
- // 6 n (^f01Next) -110 -30 100 20
- // 26 p (^f02More about Protected Mode...) 40 -205 280 20
- // 6 309 5 ; SOUND
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 5 p (^f01Prev) -215 -30 100 20
- // 7 n (^f01Next) -110 -30 100 20
- // 13 s (^f02Go to Speed chapter...) 40 -90 280 20
- // 7 310 8 ; SOUND2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 8 s (^f02If you have a Sound Blaster 16...) 40 -152 280 20
- // 9 p (^f02If you have a Pro AudioSpectrum...) 40 -130 280 20
- // 10 u (^f02If you have an UltraSound...) 40 -108 280 20
- // 11 d (^f02If you have an Diamond Sonic...) 40 -86 280 20
- // 6 p (^f01Prev) -215 -30 100 20
- // 12 n (^f01Next) -110 -30 100 20
- // 8 311 3 ; SOUND BLASTER 16
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 9 312 3 ; PRO AUDIOSPECTRUM
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 10 313 3 ; ULTRASOUND
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 11 314 3 ; <Diamond Sonic>
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 12 315 5 ; VIDEO
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 7 p (^f01Prev) -215 -30 100 20
- // 13 n (^f01Next) -110 -30 100 20
- // 27 v (^f02If you have a Diamond Viper...) 40 -62 280 20
- // 13 318 5 ; SPEED
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 12 p (^f01Prev) -215 -30 100 20
- // 14 n (^f01Next) -110 -30 100 20
- // 15 m (^f02Reducing MSCDEX Buffer Size...) 40 -61 280 20
- // 14 319 8 ; SPEED CONTINUED
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 13 p (^f01Prev) -215 -30 100 20
- // 22 n (^f01Next) -110 -30 100 20
- // 16 p (^f02If you have a Philips CD-ROM drive...) 40 -130 280 20
- // 17 m (^f02If you have a Mitsumi CD-ROM drive...) 40 -108 280 20
- // 19 n (^f02If you have an NEC CD-ROM drive...) 40 -84 280 20
- // 18 g (^f02If you have a dedicated Game Card...) 40 -62 280 20
- // 15 320 3 ; SPEED - MSCDEX
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 13 p (^f01Prev) -215 -30 100 20
- // 16 321 3 ; SPEED - PHILIPS
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 17 322 3 ; SPEED - MITSUMI
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 18 325 3 ; SPEED - SPEED CARD
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 19 326 3 ; SPEED - NEC
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 20 327 3 ; <future>
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 21 328 3 ; <future>
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 22 330 5 ; ERROR MESSAGES
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 14 p (^f01Prev) -215 -30 100 20
- // 23 n (^f01Next) -110 -30 100 20
- // 5 m (^f02Go to Memory chapter...) 40 -105 280 20
- // 23 331 4 ; ERROR MESSAGES 2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 22 p (^f01Prev) -215 -30 100 20
- // 24 n (^f01Next) -110 -30 100 20
- // 24 335 4 ; TECH SUPPORT
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 23 p (^f01Prev) -215 -30 100 20
- // 25 n (^f01Next) -110 -30 100 20
- // 25 336 3 ; TECH SUPPORT2
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 24 p (^f01Prev) -215 -30 100 20
- // 26 308 3 ; PROTECT MODE vs REAL MODE
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 5 p (^f01Prev) -215 -30 100 20
- // 27 317 3 ; VIDEO - VIPER
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 12 p (^f01Prev) -215 -30 100 20
- // 28 303 5 ; CRASHES3
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 2 p (^f01Prev) -215 -30 100 20
- // 4 n (^f01Next) -110 -30 100 20
- // 29 s (^f02If you have a SONY CD-ROM drive...) 40 -318 280 20
- // 29 337 3 ; CRASHES - SONY DRIVES
- // -1 x (^f01Exit) 10 -30 100 20
- // 0 c (^f01Contents) 115 -30 100 20
- // 28 p (^f01Prev) -215 -30 100 20
-
- #define FOO_MAN 258
- //======================================================================
- //
- // Text Pages for Manuals
- //
- //======================================================================
-
- #define MAN0 259
- // ^f01 Mortimer^f02$^f01 Interactive Manual
- //^f00
- //
- // Mortimer is a kids game.
- //
- //
- //
- //
- //
- // ^c007^f02TABLE OF CONTENTS^c001^f00
- //
- // Introduction .....................................
- //
- // Setup ............................................
- //
- // Starting a Game ..................................
- //
- // Controls .........................................
- //
- // Game Play ........................................
- //
- // Game Options .....................................
- //
- // System Info ......................................
- //
- // Data Files .......................................
-
- #define MAN1 260
- // ^f01 Introduction
- //^f00
- // ^c007^f02REQUIREMENTS^f00^c000
- //
- // Mortimer requires:
- //^f02
- // * 50MHz 486 or better PC.
- // * Double-speed, MPC Level 2 CD-ROM Drive.
- // * 8 Megabytes of memory.
- // * VGA display. (SuperVGA with VESA support for optional HiRes)
- // * DOS or Windows 95 (Windows 3.1 is NOT supported)
- //^f00^c000
- // If your system doesn't meet these requirements, Mortimer may not run satisfactorily. In addition,
- // for sound you'll need a Sound Blaster, Pro AudioSpectrum, Ultrasound, Aria, Soundscape or compatible
- // sound card. You should run the game without a memory manager. The easiest way to do this is by
- // creating a boot disk using the "Make Boot Disk" option in the Main Menu and booting off this disk.
- //
- // ^c007^f02OVERVIEW^f00^c000
- //
- // Mortimer is divided into two modules--the Launcher/Config Utility and the Game Module.
- // The Launcher Utility contains menus to configure the game for your system and play preferences.
- //
- // Whenever you start Mortimer, you'll begin in the Launcher/Config Utility. Here,
- // you can bring up this manual, access the game's troubleshooting guide, setup configuration settings,
- // customize the game, and make a boot disk. Finally, you'll find the "Play Game" selection, which takes
- // you to the Game Module, where you can play the game using the current settings.
- // ^c001^f02Continued...
-
- #define MAN1_5 261
- // ^f01 Introduction Continued
- //^f00
- // ^c007^f02SETUP^f00^c000
- //
- // Before running the game for the first time, you must configure the Launcher so it understands
- // how to communicate properly with your computer and peripherals. When you run the Launcher for
- // the very first time, it will automatically offer you the option of "Auto-Detecting" your
- // computer's settings for you. This means that the Launcher will test your computer and do its best
- // to guess appropriate settings. If you choose not to Auto-Detect at that time, you may
- // still do so by choosing the "Auto-Detect" option under the Setup menu. Note that some sound cards
- // may cause false detection of a joystick, even if one is not present. If this happens, use the
- // "Setup" menu to change your default controller back to mouse or keyboard before starting the game.
- //
- // You can bring up the Setup menu by choosing "Setup" from the Launcher's main menu. The
- // Setup menu allows you to change sound, video, and game play settings used by the Game Module.
- // The settings shown in the Setup menu should match those of your machine. If you are unsure
- // of what your machine's settings are, you should choose "Auto-Detect" and have the program
- // set these values for you. A description of the different settings appears on the following page.
- //
- // ^c007^f02STARTING THE GAME^f00^c000
- //
- // Once your settings are correct, run the Game Module by choosing the "Play Game" option from the
- // main menu. Depending on the utilities/memory managers you have loaded on your computer, you
- // may first need to make a boot disk (using the "Make Boot Disk" option) in order to run the game
- // properly. You will also need to reboot your computer using the boot disk for the changes to take
- // effect.
-
- #define MAN2 262
- // ^f01 Setup
- //^f00
- // The setup menu contains the following options:
- //
- // ^f02^c007AUTO-DETECT^c000^f00
- // Use this option to recognize appropriate settings for your machine.
- //
- // ^f02^c007SOUND CARD^c000^f00
- // Use this option to select the sound card in your computer, or (none) if you do not have one.
- //
- // ^f02^c007TEST SOUND^c000^f00
- // Use this option to test your sound settings. If they are set properly, you should hear
- // music. If you have a stereo sound card, it should play first from the left and then to right.
- //
- // ^f02^c007IRQ^c000^f00
- // Use this option to set the IRQ channel used by your sound card.
- //
- // ^f02^c007BASE^c000^f00
- // Use this option to set the Base address used by your sound card.
- //
- // ^f02^c007DMA^c000^f00
- // Use this option to set the DMA channel used by your sound card.
- //
- // ^f02^c007SPEAKER ORIENTATION^c000^f00
- // Use this option to exchange how the program uses your left-right stereo speakers.
- // ^c001^f02Continued...
-
- #define MAN3 263
- // ^f01 Setup Continued
- //^f00
- // ^f02^c007DETAIL LEVEL^c000^f00
- // Use this option to select the default level of detail the animation engine will run at. A
- // higher detail level will yield better image quality but a reduced frame rate on slower machines.
- //
- // ^f02^c007RESOLUTION^c000^f00
- // Use this option to set the game's resolution. In order to use a resolution
- // other than Low, you'll need a VESA-compatible SuperVGA video card, monitor, and properly
- // installed VESA drivers. When you do, SysInfo reports your video card driver as "VESA."
- //
- // ^f02^c007ADVANCED SETTINGS^c000^f00
- // Use this option to adjust advanced settings to optimize the performance of your system.
- // Warning: Casually altering these values may lockup your system.
- //
- // ^c007TIMER RATE^c000 - Adjusts the multitasking timer or switches to sequential (cooperative) mode.
- //
- // ^c007FRAME RATE^c000 - Adjusts the maximum frame rate. Lower this setting to smooth out play with
- // slower CD drives.
- //
- // ^c007SAMPLE RATE^c000 - Adjusts the rate of the system's internal sound engine. Default is 11025 Hz.
- //
- // ^c007VIDEO DRIVER^c000 - Allows you to use UNIVBE to override an existing VESA video driver.
- //
- // After you have selected your settings, choose CONTINUE. You will be asked if you want to save your
- // changes to a file on your hard drive. You do not need to save your changes to use them, but if you
- // do not, your selections will be lost when you quit Mortimer.
-
- #define MAN4 264
- // ^f01 Starting a Game
- //^f00
- // Choose "Play Game" from the Launcher/Config Utility. The Game Module will be initialized
- // with your configuration settings, and will start the opening demo loop of the game. Press a key
- // on the keyboard or press the Fire button on your selected game controller to exit the demo. This
- // will take you to the Main Menu of the Game Module.
- //
- // ^f02^c007MAIN MENU^c000^f00
- //
- // The Main Menu contains options to calibrate your joystick (if it's the selected controller), set
- // game options, resume the demo, return to the Launcher Utility, or begin the game. Select a menu item
- // by moving your controller up and down. Click on the Fire button to select an option or press "Enter."
- //
- // ^f02^c007PILOT MENU^c000^f00
- //
- // Before beginning a game, you will need to choose a pilot, or create one if you are playing
- // for the first time. When you play using a particular pilot, your strength and score are saved
- // each time you complete a chapter of the game. That way, if you quit the game, you can return
- // later to the same chapter. In addition, once a pilot has completed chapters, you can go
- // back and replay any of them, trying to improve your score or strength. These new results will
- // overwrite your initial attempts.
- //
- // To create a new pilot, choose the "Add New Pilot" menu item. You will be asked to choose
- // a difficulty level for the new pilot. There are four standard difficulty levels, ranging from
- // "Novice" to "Expert," and two custom difficulty levels. The custom difficulty levels can be
- // adjusted using the difficulty editor found in the Launcher Utility. A new pilot will be created
- // with a default name. To change the name, simply backspace over the old name and type a new one.
- //
- // ^c001^f02Continued...
-
- #define MAN5 265
- // ^f01 Starting a Game Continued
- //^f00
- // You can delete a pilot or make a copy of one using the corresponding menu item. You may wish
- // to copy a pilot to "back it up" before replaying a previously completed chapter.
- //
- // To continue with a chosen pilot, select it with the Fire button on your controller.
- //
- // ^f02^c007CHAPTER MENU^c000^f00
- //
- // The Chapter Menu allows you to play where you left off last time or to replay a completed chapter.
- // If you are playing with a new pilot, only Chapter 1 will be available. To play Chapter 2, you must
- // first qualify for it by completing Chapter 1 and so on.
- //
- // Alternatively, you can qualify for a chapter by entering the correct passcode for that chapter.
- // Passcodes to replay a particular chapter are displayed after completing that chapter. There is a
- // different set of passcodes for each difficulty level, so you can only use a passcode if it was
- // obtained after finishing the level using a pilot with the same difficulty.
- //
- // To begin playing a particular chapter, select it and press Fire.
-
- #define MAN6 266
- // ^f01 Controls
- //^f00
- // Mortimer can be played with a joystick, mouse, or keyboard. You must choose which control
- // to use in the Launcher Utility before beginning the game.
- //
- // ^f02^c007JOYSTICK CONTROL^c000^f00
- // Mortimer performs a rough joystick auto-calibration when it begins, but you can recalibrate
- // manually using the "Calibrate Joystick" item in the Game Main Menu or by pressing 'j' during game play.
- //
- // You will be asked to:
- // 1) Center the joystick and click the Fire button,
- // 2) Move the stick to the upper left and click the Fire button,
- // 3) Move to the lower right and click the Fire button, and finally
- // 4) Center the stick and click the Fire button again.
- //^c000
- // ^f02^c007KEYBOARD KEYS^c000^f00
- //
- // ^f00 - Options Screen
- //
- // ^f00 - Joystick Calibration
- //
- // ^f00 - Abort Mission in Progress
- //
- // ^f00 - Quit to Launcher
- //
- // ^f00 - Escape Thru Cutscenes
- //
- // ^f00 - Pause the Game ^c001^f02Continued...
-
- #define MAN7 267
- // ^f01 Controls Continued
- //^f00
- //
- // ^f02^c007MANEUVERING^c000^f00
- //
- // S T^f00
- //
- //
- //
- //
- //
- //
- //
- //
- //
- //
- //
- //
- // ^f02^c007 Joystick Control Mouse Control Keyboard Control^f00^c000
- //
- //
- // Note: You can optionally reverse the up/down controls by choosing the "Controls Flipped" item in
- // the Options Menu.
-
- #define MAN8 268
- // ^f01 Game Play
- //^f00
- // Game play for various chapters follows one of these four models:^f00
- //^f00 ^f02^c007IN-COCKPIT FLIGHT^c000^f00
- // Moving your controller moves your ship and aims your target sight. Shoot targets
- // that become available by pressing Fire. Dodge other targets by steering your ship
- // away from them. If you do not, you will collide with them and take damage. Note
- // that when dodging, it takes time for the ship to move in whatever direction you
- // point the cursor. Thus, you must plan and act ahead to steer clear of obstacles.
- //
- //^f00 ^f02^c007GROUND COMBAT^c000^f00
- // Use your controller to move your gun, aiming it at enemies. Note that you must
- // control up/down as well as left/right motion. Shoot using the Fire button. Use
- // the secondary action button to take cover behind obstacles, if available. On some
- // levels, when taking cover, you can use your controller to select which direction
- // to emerge when you release the action button.
- //
- //^f00 ^f02^c007BEHIND-SHIP FLIGHT^c000^f00
- // Pull your controller back to rise, forward to fall, or left or right to bank.
- // Note that like in a plane, you acheive your strongest turning power by first
- // banking and then pulling back the stick. Be gentle, though--do not over-steer
- // your craft.
- //
- //
- //^f00 ^f02^c007POINT-OF-VIEW COMBAT^c000^f00
- // Use your controller to move your body and to look/aim at targets. Press the Fire
- // button to fire your lasers.
- //
- // ^c001^f02Continued...
-
- #define MAN9 269
- // ^f01 Game Options
- //^f00
- // The Options Menu is available under the Main Game Menu or by pressing 'o' during game play.
- //
- // ^f02^c007Music On/Off
- //^c000^f00 Turns on or off music during the game.
- // ^f02^c007SFX On/Off
- //^c000^f00 Turns on or off sound effects.
- // ^f02^c007Voices On/Off
- //^c000^f00 Turns on or off voices.
- // ^f02^c007Text On/Off
- //^c000^f00 Turns on or off dialog subtitle text.
- // ^f02^c007Controls Normal/Flipped
- //^c000^f00 Optionally reverses the up/down functionality of your controller.
- // ^f02^c007Rapid Fire On/Off
- //^c000^f00 Optionally causes lasers to keep firing as long as Fire button is held down
- // ^f02^c007Joystick Speed
- //^c000^f00 Adjusts sensitivity of joystick (available only if controller is joystick)
- // ^f02^c007Volume Level
- //^c000^f00 Set the volume level of your sound card (if supported).
- // ^f02^c007Detail Level
- //^c000^f00 Sets the detail level of displayed graphics.
- // ^f02^c007Brightness Adj
- //^c000^f00 Adjusts the overall brightness (gamma level) of graphics.
-
-
-
- #define MAN8_5 272
- // ^f01 Game Play Continued
- //^f00
- // ^f02^c007SCORING^c000^f00
- // You are awarded points for shooting targets, dodging enemies, and for elapsed time in
- // time-critical chapters. These points accumulate from chapter to chapter as you advance through the
- // game. When you end a game, successfully or not, your score qualifies you for a position on the
- // high-scores list.
- //
- // During game play, your score may award you extra lives. You earn one free life at regular
- // intervals as you accumulate points. The intervals vary with difficulty level and are as follows.
- //
- // Beginner - Every 5000 points
- // Novice - Every 10000 points
- // Standard - Every 15000 points
- // Expert - Every 20000 points
- //
- // ^f02^c007RANKING^c000^f00
- // In addition, you are also awarded rank medals based on your target accuracy and flight
- // performance on each level. Like points, rank medals also accumulate and appear on the high
- // scores list. They have the following values:
- //
- // ^f00 1 Rank unit
- // ^f00 3 Rank units
- // ^f00 9 Rank units
- //
- // Whenever you earn a medal, you receive a corresponding point bonus as well.
-
- #define BOOTDISK 273
- // ^f01 BootDisk Maker
- //^f00
- //
- // ^f02^c007MAKING A BOOT DISK^c000^f00
- //
- // Run the bootdisk maker by choosing "Make Boot Disk" from the Launcher's Main Menu. This utility
- // will create a startup disk, or boot disk, tailored to run the game on your system. It requires a
- // clean, high-density diskette that fits into your system's A: drive. After you create a boot disk, you
- // will need to restart your computer using the boot disk to take advantage of the changes. You will
- // need to do this each time before starting Mortimer.
- //
- // If the bootdisk maker crashes when run from the launcher, run it manually at the DOS prompt from
- // the CD's SUPPORT directory. Type "SUPPORT\BOOTDISK" and press <Return>. The problems may occur if
- // you do not have enough low memory for both the Launcher and bootdisk maker to run at the same time.
- // This is especially true under Windows 95 and DOS 7.0, whose system files have grown to take up more
- // low memory.
- //
- // ^f02^c007USING A BOOT DISK^c000^f00
- //
- // To use your boot disk, insert the boot disk into your computer's A: drive (and close the drive's
- // door, if any) and restart the system. Your system can most easily be restarted by pressing the RESET
- // button, often located on the front panel of your computer case. If your system does not have a RESET
- // button, restart it by holding down the keyboard's CONTROL, ALT, and DELETE keys simultaneously. An
- // alternative is to turn off your computer, wait 15 seconds, and then turn it back on.
-
-
- #define FILE1 274
- // ^f01 Files
- //^f00
- // Mortimer stores a number of files on your C: drive in the MORTIMER\ directory. If this
- // directory is not present, it will be created when the files are first written. The files are:
- //
- // ^f02^c007MORTIMER.CFG^c000^f00
- // Contains all your Sound/Video/Options settings. If the launcher cannot find this file, it will
- // prompt you for auto-detection when you start the launcher.
- //
- // ^f02^c007MORTIMER.PIL^c000^f00
- // Contains your pilot names, ranks and standings. If deleted, you will start with no pilots.
- //
- // ^f02^c007MORTIMER.PRF^c000^f00
- // Contains in-game control, volume, and display preferences. If not present, default values are used.
- //
- // ^f02^c007MORTIMER.CUS^c000^f00
- // Contains values for your custom difficulty levels. If not present, default values are used.
- //
- // ^f02^c007MORTIMER.PTS^c000^f00
- // Contains the high scores list. To clear the high scores list, delete this file by pressing the
- // button below.
- //
- //
- //
- //
- // You may also install Mortimer's files in a custom directory of your own. For instructions...
-
- #define FILE_CUSTOM 275
- // ^f01 Files - Custom Install
- //^f00
- // You may optionally have Mortimer save its settings in a separate directory of your choosing
- // instead of the default directory C:\MORTIMER. To do this, simply run MORTIMER passing it a path to the
- // directory for the files. For instance, if you have a "GAMES" directory on your C: drive, you can
- // have Mortimer store its files there. Every time you start the game, simply pass it a path
- // to the directory as follows:
- //
- // ^f02^c007 MORTIMER C:\GAMES^c000^f00
- //
- // Keep in mind that the save directory must already exist and you must be at the prompt of your
- // CD-ROM drive, not in your save directory. Also, you must add the extra parameter every time or the
- // game will not be able to find previously-saved settings.
- //
- // You may wish to make a batch file to do this every time. This batch file can reside on your hard
- // drive in your save directory. When run, it will change to the CD-ROM drive and run MORTIMER with
- // a path back to the save directory.
- //
- // For instance, if your CD-Rom drive is drive D: and you've created a directory called "GAMES" on
- // your C: drive, you might want to create a file MORTIMER.BAT in the GAMES directory that contains the
- // following 3 lines:
- //
- // ^f02^c007D:^c000^f00
- // ^f02^c007MORTIMER C:\GAMES^c000^f00
- // ^f02^c007C:^c000^f00
- //
- // To run it, change to the save directory and type MORTIMER. Do this every time instead of running
- // from the CD drive.
-
- #define SYS1 276
- // ^f01 SysInfo
- //^f00
- // The SysInfo routines test the four main components of your system critical to running
- // Mortimer: Memory, Processor, CD-ROM Drive, and Video System. It rates them as follows:
- //
- // ^f02^c007 Insanely Happy Face^f00^c000
- // This component is exceptional and good bragging material.
- //
- // ^f02^c007 Happy Face^f00^c000
- // This component is comfortably above minimum requirements and should run the game well.
- //
- // ^f02^c007 Neutral Face^f00^c000
- // This component is adequate for running the game.
- //
- // ^f02^c007 Sad Face^f00^c000
- // This component is below specifications for running the game and may result in poor
- // performance, depending on the other components in your system.
- //
- // These are approximate ratings; your mileage may vary. In general, your performance will
- // reflect the combined performance of all four system components. Processor and CD-ROM drive are the
- // most important. If either are particularly poor, your total performance will suffer. On the other
- // hand, having much memory above the minimum will have little effect on overall performance.
- // ^c001^f02Continued...
-
- #define SYS2 277
- // ^f01 SysInfo Continued
- //^f00
- //^c007^f02 MEMORY ^c000^f00
- //
- // The memory window shows the total and free "protected-mode" memory available in your system.
- // This is the amount of XMS that has not been allocated away by a memory manager to be used as EMS.
- // Some memory managers allocate all the XMS it plans to use at boot-time, while others only do so as
- // EMS is requested. The first case can cause the most problems, as an EMS manager might allocate
- // away much or all of your XMS memory, leaving none for Mortimer.
- //
- // Mortimer requires at least 6 Megabytes of "protected-mode" memory to run, but does not use
- // base memory (memory below 640k) or EMS memory. Therefore, it is not necessary to have a memory
- // manager installed when running Mortimer. In fact, some memory managers actually interfere
- // with Mortimer, causing bugs or slow-downs. If your default system configuration includes
- // a memory manager (most do), you should make a boot disk and boot off of it before running
- // Mortimer, especially if you encounter slow performance, crashes, or other unexplained bugs.
- //
- //^c007^f02 PROCESSOR ^c000^f00
- //
- // The processor window shows your computer's CPU type and approximate speed.
- //
- // A 50Mhz '486 or better is recommended. Your actual results may vary, depending on what
- // caches are installed in your machine and the speed of other components.
- //
- //
- //
- //
- //
- // ^c001^f02Continued...
-
- #define SYS3 278
- // ^f01 SysInfo Continued
- //^f00
- //^c007^f02 CD DRIVE ^c000^f00
- //
- // The CD window shows your system's CD drive letter and speed. The speed is measured as the
- // sustainable transfer rate when running using a regulated percentage of total computing power.
- //
- // Mortimer requires a sustained transfer rate of 225 kilobytes per second (kps) to run at a
- // full 15 frames per second. Ideally, this should be accomplished with as little CPU-usage (computing
- // power taken up) by the CD drive as possible, leaving more processor power for running the game.
- //
- // The MPC level-2 specification requires a CPU-usage of less than 60% to maintain a transfer rate
- // of 300 kbs. Ideally an MPC drive should take proportionally less CPU time (45%) to transfer
- // Mortimer's requirement of 225 kps. Unfortunately, many new IDE CD-ROM drives sold in multimedia
- // upgrade packs do not meet this requirement or even MPC specifications, even if advertised to do so.
- // Some take as much as 70% or more of your system's precious computing power just to read from the CD.
- //
- // If you have such a drive, the game will automatically adjust your CD-Drive CPU-Usage to a
- // higher value to achieve smoother motion. On a slower machine, this may mean animations will run at
- // less than 15 frames per second.
- //
- //^c007^f02 VIDEO ^c000^f00
- //
- // The video window shows how fast information can be written to your video card. While this
- // is somewhat dependent on the speed of your computer, it is largely determined by the speed and
- // type of video card you have.
- //
- // The speed of your video card can make a significant difference in the speed games run. This
- // may be particularly important on slower machines. In general, PCI and Local Bus (VLB) are much faster
- // than standard bus video cards. Most new machines today can accommodate one of the two faster standards.
-
-
-
-
- #define TROUB 300
- // ^f01 Mortimer^f02$^f01 TROUBLESHOOTING GUIDE
- //^f00
- // The majority of problems experienced with Mortimer are the result of hardware conflicts or
- // improper configuration on one's computer. Mortimer uses a computer to its fullest potential.
- // Thus, minor conflicts may occur when playing Mortimer, even if the computer seems to
- // behave properly with other software.
- //
- // The first step in diagnosing a problem running Mortimer is to isolate the conditions under
- // which the problem occurs. Please use this interactive troubleshooting manual to aid in your debugging
- // procedure.
- //
- // If you are unable to resolve the problem you are encountering, call technical support at the
- // numbers listed at the end of this manual or contact us online or by fax.
- //
- // ^c007^f02TABLE OF CONTENTS^c001^f00
- //
- // Crashes and lockups ......................
- //
- // Joystick problems and concerns ...........
- //
- // Memory problems and concerns .............
- //
- // Audio problems and concerns ..............
- //
- // Video problems and concerns ..............
- //
- // Speed problems and concerns ..............
- //
- // Error messages ...........................
- //
- // Technical support ........................
-
-
- #define TROUB_CRASH1 301
- // ^f01 Crashes/Lockups
- //^f00
- // ^f02^c007CLEANING YOUR CD^c000^f00
- //
- // If you are experiencing crashes running Mortimer, first try cleaning your CD, wiping it
- // gently with a soft cloth. (Move in smooth strokes from the center hub to the outer edge of the CD.)
- // If this does not help, you most likely have a DMA and/or IRQ conflict involving your mouse, sound
- // card, or another device in your computer.
- //
- // ^f02^c007SMARTDRIVE / CD-CACHING SOFTWARE^c000^f00
- //
- // CD-caching and/or disk-caching software can confuse Mortimer if the CD drive encounters a read
- // error. If you are having problems, disable caching software and caching options of your CD driver.
- //
- // ^f02^c007MAKE A BOOT DISK^c000^f00
- //
- // If you have not done so already, make a boot disk using the the "Make Boot Disk" option
- // under the main menu of this launcher. Reboot off the boot disk and see if the problem remains.
- // If it disappears, you most likely have a memory manager or utility whose operation conflicts with
- // Mortimer. Boot off the boot disk from now on to insure that the conflict is avoided.
- //
- // ^f02^c007SOUND/CONTROLLER CONFLICTS^c000^f00
- //
- // If the problem remains, try running the game with "None" as the selected sound card and "Keyboard"
- // selected as the controller. If symptoms disappear, your mouse and/or sound card most likely conflict
- // with another device in your computer or with each other. Consult the documentation that came with your
- // mouse or sound card for specific instructions on how to configure those items so they don't conflict.
- //
- // ^c001^f02Continued...
-
- #define TROUB_CRASH2 302
- // ^f01 Crashes/Lockups Continued
- //^f00
- // ^f02^c007INTERRUPT CONFLICTS^c000^f00
- //
- // You may be able to resolve some problems by insuring the animation system is running in cooperative
- // (sequential) mode and not preemptive (interrupt-driven) mode. Do this by checking that the
- // "sequential" switch under the "Multitasking" menu item is checked. This switch is found under the
- // "Advanced Settings" item in the Setup Menu. Playing with a joystick and not a mouse may also help.
- //
- // ^f02^c007DOS EXTENDER CONFLICTS^c000^f00
- //
- // Crashes while running Mortimer may occur due to conflicts between certain machine
- // configurations and the DOS extender, DOS4GW. You can often resolve such conflicts by using a
- // different version of DOS4GW. A few recent versions of DOS4GW reside on this CD. To install a
- // different version of DOS4GW, press one of the buttons below. The appropriate version will be copied
- // to the C:\MORTIMER\ directory. When you exit Mortimer and re-enter, this version will be used
- // instead of the default version on the CD.
- //
- //
- //
- // If you cannot install a new version of DOS4GW because of lockups in the Launcher program, install
- // them from a DOS prompt by running one of the following files from the CD's SUPPORT directory:
- //
- // To install version 1.97, type:^c007 \SUPPORT\INST197^c000 and press the Enter key.
- // To install version 1.95, type:^c007 \SUPPORT\INST195^c000 and press the Enter key.
- // To install version 1.92, type:^c007 \SUPPORT\INST192^c000 and press the Enter key.
- //
- // Under Windows 95, simply open the SUPPORT directory and double-click the corresponding icon.
- //
- // ^c001^f02Continued...
-
- #define TROUB_CRASH3 303
- // ^f01 Crashes/Lockups continued
- //^f00
- // ^f02^c007SYSTEM-SPECIFIC INFORMATION^c000^f00
- //
- //
- //
- //
- //
- // ^f02^c007WINDOWS 95^c000^f00
- //
- // When running under Windows 95, be sure to turn off all other utilities and programs before running
- // Mortimer. Specifically, be sure to disable any network-based mail programs, as incoming mail
- // messages may disrupt or interfere with game program flow or controller operation. If you only have
- // eight megabytes of memory, be especially sure you aren't running utility programs such as screen-
- // savers, wallpaper, or anti-virus programs that might use up memory. In addition, if you
- // leave the game minimized on your task bar for an extended period of time, you may lose controller
- // functionality. Generally, we do not recommend switching away from the game during a play session.
- //
- // ^f02^c007WINDOWS 95 MSDOS MODE^c000^f00
- //
- // When running under MSDOS Mode under Windows 95, be sure you have proper 16-bit drivers installed
- // for your sound card and CD-ROM drive. If you purchased your system with Windows 95 installed, these
- // drivers may not have been pre-installed for you. Contact your hardware manufacturer for more
- // information on obtaining and installing these drivers.
-
- #define TROUB_JOY 305
- // ^f01 Joystick/Control
- //^f00
- // ^c007^f02JOYSTICK TYPE^c000^f00
- //
- // Mortimer supports analog joysticks only. Digital joysticks, like the ones that
- // resemble video game controllers, will not work properly. The game does not support the extra
- // buttons on the Flightstick Pro or Thrustmaster joysticks. Also, remember to plug in your joystick
- // before running Mortimer.
- //
- // ^c007^f02JOYSTICK CONTROL^c000^f00
- //
- // If you are having problems with joystick control, first check to see if you have
- // more than one joystick port enabled on your PC. If you do, you should disable one of the ports
- // so they do not conflict. In general, the joystick port on your sound card is less likely to have
- // compatibility problems. If the joystick seems too sensitive, make sure any trim controls on the
- // joystick are adjusted to give you a full range of motion. Also, after plugging in a joystick, you
- // should recalibrate using the 'j' key.
- //
- // If the controls still seem too sensitive, try adjusting your joystick speed in the game "Options"
- // menu. A lower value will slow the joystick and reduce jerkiness. You may also wish to slow down the
- // game by adjusting the "Frame Rate" in the Advanced Setup menu.
- //
- // ^c007^f02MOUSE DRIVER CONFLICTS^c000^f00
- //
- // Mortimer may exhibit odd behavior due to a conflict with some mouse drivers. To
- // determine if this is the case, don't load your mouse driver and try running the game from the keyboard
- // or a joystick. If the conflict still exists, try running with a recent version of Microsoft's mouse
- // driver.
-
-
- #define TROUB_MEM 307
- //
- // ^f01 Memory
- //^f00
- // ^c007^f02REQUIREMENTS^c000^f00
- //
- // Your machine requires 8 Megabytes of memory to run Mortimer properly. The amount of low
- // memory (below 640k) is not important because the game runs almost entirely in "protected-mode" high
- // memory. You should not, however, run a memory manager, since some memory managers allocate too much
- // high memory for themselves. Furthermore, running a memory manager will almost always slow down
- // Mortimer, and in some cases will cause the game to crash. The best way to make sure you are not
- // running a memory manager is to use a boot disk.
-
- #define TROUB_MEM_PROT 308
- //
- // ^f01 Memory - Protected Mode
- //^f00
- // ^c007^f02PROTECTED MODE vs REAL MODE^c000^f00
- //
- // Mortimer runs in your computer's native "protected" mode. Many programs, however, still
- // run in what is called "real" mode, which allows Intel processors to emulate the 8088 chip found in the
- // original IBM PC. One of the many limitations of running in "real" mode is that programs must fit
- // entirely in a computer's lower 640k of memory and cannot access the memory above one Megabyte without
- // a memory manager like EMM386 or 386Max. The purpose of these utilities is to allow older "real" mode
- // programs to "see" memory above one megabyte and also to maximize the amount of low (below 640k) memory
- // available for these programs to fit into.
- //
- // Since Mortimer runs in "protected" mode, it doesn't care how much "low" memory exists and
- // high memory is just as easy for the game to use as low memory. Therefore, Mortimer does not need a
- // memory manager to run. In fact, some memory managers allocate all of a system's memory for real-mode
- // emulation, leaving none for "protected-mode" programs to run. Furthermore, memory managers often slow
- // down or crash "protected-mode" programs, so it's best to run with no memory manager at all.
- //
- // Since you'll probably want to still run your normal "real" mode programs after playing the
- // game, you'll only want to disable your memory manager temporarily. The best way to do this is to make
- // a boot disk using the "Make Boot Disk" option under the Main Menu of this program. Boot off
- // the boot disk before playing the game and reboot off your hard drive before returning to work.
- // Alternatively, you can create a special "game boot" menu in your AUTOEXEC.BAT if you are running
- // under DOS6.0 or higher. This is called a "Multi-Boot," and instructions for making one are in your
- // DOS6.0 owner's manual.
-
- #define TROUB_AUDIO 309
- // ^f01 Audio
- //^f00
- // Most sound problems occur because the sound settings chosen under the "Setup" menus of this
- // launcher do not match the settings of your sound card.
- //
- // ^c007^f02NO SOUND^c000^f00
- //
- // If you are not getting any sound, make sure you have a sound card supported by the game and
- // that the sound card chosen under the "Sound Card" menu is correct for your hardware. If you are
- // unsure of your sound card's settings, choose the "Auto Detect" option, which automatically fills-in
- // the correct sound card and settings for most systems.
- //
- // Running in MSDOS mode under Windows 95, be sure you have proper 16-bit drivers installed.
- //
- // ^c007^f02POOR SOUND QUALITY^c000^f00
- //
- // If you hear echoing or crackling, you most likely have an IRQ or DMA conflict between
- // your sound card and another device in your computer. Try reconfiguring your sound card to another
- // IRQ number or DMA channel, following your sound card's instruction manual.
- //
- // ^c007^f02SLURRED SOUND^c000^f00
- //
- // Slurred sound is usually a result of a general slow-down of your system, often from a problem
- // with a CD-ROM drive or the presence of a memory manager. See the "SPEED" chapter of this manual
- // for ways to improve performance.
- //
- //
- //
- //
- // ^c001^f02Continued...
-
- #define TROUB_AUDIO2 310
- // ^f01 Audio Continued
- //^f00
- // ^c007^f02SOUND CARD VOLUME^c000^f00
- //
- // A volume control exists in the Options Menu, which can be accessed either at the beginning of the
- // game from the Launcher Main Menu or at any time by pressing the 'o' key. To change volume, select
- // the volume item and move your controller left or right while holding down the fire button.
- //
- // Note that some sound cards, such as an original Sound Blaster, do not have a software-controllable
- // volume control; therefore, this menu will not be available when using a Sound Blaster Compatible.
- //
- // Also note that for the Pro AudioSpectrum, you should use the hotkey-activated TSR to change
- // volume instead of the game's volume control. To do so, first pause the game to allow the TSR access
- // to the keyboard. This applies to any TSR which is activated through the keyboard. Even if you do
- // not wish to change volume during the game, you should install the TSR on your hard drive. If it is
- // not installed, the sound card may default to no volume when your system is first booted up. (Refer
- // to your sound card documentation for further information about this TSR.)
- //
- // For card-specific debugging information, refer to the following sections:
-
- #define TROUB_AUDIO_SBL 311
- // ^f01 Audio - Sound Blaster 16 / AWE32
- //^f00
- // If you are using a Sound Blaster 16 in 16-bit mode, you must configure Mortimer
- // to use the 16-DMA channel (default=5) your card is set to. This is not necessarily the same as your
- // 8-bit DMA channel (default=1). You can check your card's setting by looking in your AUTOEXEC.BAT
- // file for the "SET BLASTER" command, or typing "SET" at a DOS prompt and pressing the Enter key. The
- // 16-bit DMA channel is preceeded by an "H", while the 8-bit channel follows a "D". The game's
- // Auto-Detect feature will choose this value properly.
- //
- // Some motherboards don't work well with DMA channels higher than 3, resulting in crackling or
- // echoing sound. If you are experiencing this problem, try configuring your sound card to use a lower
- // channel for both 16 and 8-bit DMA. Please refer to your sound card documentation for instructions on
- // how to change your 16-bit DMA channel. It's usually safest to simply change the 16-bit DMA channel
- // to the same setting as the 8-bit DMA channel (typically 1). You will still get 16-bit sound, even
- // with 8-bit DMA.
- //
- // Once you've completed the changes, reboot your machine so that they can take effect. Your sound
- // card configuration program should have changed your "SET BLASTER" command in your AUTOEXEC.BAT file
- // to reflect the change. Thus, if you type "SET" at a DOS prompt and look for the "BLASTER" line, the
- // number following the "H" should match the number following the "D".
-
- #define TROUB_AUDIO_PAS 312
- // ^f01 Audio - Pro AudioSpectrum
- //^f00
- // Mortimer supports the Pro AudioSpectrum sound card in its native mode.
- //
- // ^c007^f02CRACKLING/ECHOING^c000^f00
- // This is most likely caused by a DMA conflict, possibly between the native half of the sound
- // card and the Sound Blaster emulation half. Try changing the DMA channel on both the card and in the
- // setup menus to another value. Using a 16-bit DMA channel (5,6 or 7) works well in most cases. Some
- // system mother boards, however, do not do 16-bit DMA well. If this is the case, try DMA 0 or 3.
- // You will still get 16-bit sound. To make the change, edit the CONFIG.SYS file on your boot disk,
- // modifying the D:<x> parameter in your MVSOUND.SYS line to D:5 or D:6, etc. Also you may wish to
- // turn off Sound Blaster emulation by using the S:0 (zero) parameter. Reboot your machine, and
- // remember to reset the settings in the sound setup to match your changes. (For further info, refer
- // to your sound card documentation.)
- //
- // ^c007^f02STATIC/POPPING^c000^f00
- // This is most likely due to an IRQ conflict. Try changing the Q:<x> parameter in your MVSOUND.SYS
- // line in your boot disk's CONFIG.SYS to a different number (valid values are 2,3,5,7,10,11,12, and 15),
- // and make sure to reboot after the change is made. Popping seems often associated with using IRQ 7.
- //
- // To cure a steady popping sound, try adding the T:1 parameter to the end of the MVSOUND.SYS line
- // in your boot disk's CONFIG.SYS.
- //
- // ^c007^f02NO SOUND^c000^f00
- // If you cannot hear sound, make sure the volume on the card is turned up and you have the sound
- // card TSR installed. Use the hot key combinations CTRL+ALT+U to turn up the volume and CTRL+ALT+D to
- // turn down the volume. Keep in mind that TSR hot keys only work when the game is paused.
- //
- // If you cannot get the card to work, re-enable Sound Blaster emulation and set your sound card type
- // in the launcher to "Early Sound Blaster" or "Standard Sound Blaster".
-
- #define TROUB_AUDIO_ULTRASOUND 313
- // ^f01 Audio - UltraSound
- //^f00
- //
- // ^c007^f02CRASHES^c000^f00
- // If you are getting DOS4GW errors when trying to auto-detect your sound card. Try changing the base
- // address of the card to a different value. Some reports indicate base address 240 may be more
- // problematical than other addresses.
- //
- // The UltraSound driver is somewhat CPU-intensive. Thus, you experience some slowdown for loss of
- // lip-sync when running sound on an UltraSound. Also, the current UltraSound driver is mono only to
- // help reduce processing burden on the CPU. This may affect mouse controllability on some machines.
- // If this is the case, try joystick instead.
- //
-
- #define TROUB_SONIC 314
- // ^c007^f02DIAMOND SONIC^c000^f00
- //
- // If you have a Diamond Sonic sound card, be aware that at least one version of the manufacturer's
- // install software fills in an incorrect base address value in the SET ARIA line of your AUTOEXEC.BAT.
- // This may cause Mortimer's auto-detect to crash your machine or detect the wrong value. If this
- // happens, fill in the correct base address value manually instead of using the auto-detect.
-
- #define TROUB_VIDEO 315
- // ^f01 Video
- //^f00
- // ^c007^f02HIGH RESOLUTION SUPPORT^c000^f00
- //
- // In order to run the game in interlaced or high resolution, you need a video card that supports
- // the VESA video standard, either directly or through a compatible VESA video driver. This driver
- // must be installed and running for high resolution to work. Furthermore, your video card must
- // support either of the following video modes:
- //
- // 640 x 400 x 256-color
- // 640 x 480 x 256-color
- //
- // If the latter resolution is supported but not the former, Mortimer will run slightly
- // letterboxed in the middle of the screen in high-resolution mode.
- //
- // If you do not know if your system is setup to support VESA, run SysInfo from the main menu.
- // If you are not setup to support VESA video modes, your video card type will be displayed
- // simply as "VGA."
- //
- // If this is the case, you still may be able to run VESA modes on your video card using the
- // included universal VESA driver UNIVBE. If you try to start the game in high resolution but have
- // not loaded a VESA driver, the launcher will prompt you to automatically try to run UNIVBE first.
- //
- // Even if your video card is setup for VESA, you may get better results in some cases by running
- // UNIVBE instead of your default driver. If this is the case, use the "Force UNIVBE" option in the
- // Advanced Setup Menu.
- //
- // UNIVBE is a product of SciTech Software, (c)1993-1995 SciTech Software
-
- #define TROUB_VIDEO_VIPER 317
- // ^f01 Video - Diamond Viper
- //^f00
- // ^c007^f02HIGH RESOLUTION SUPPORT^c000^f00
- //
- // You can run the game in high resolution on the PCI version of the Viper card using the VESA video
- // driver that came with your card. The driver is called VPRMODE.EXE and is typically installed in a
- // C:\VIPER directory on your hard drive. To enable VESA support, go into this directory and type:
- //
- // ^c007^f02VPRMODE VESA^f00^c000
- //
- // or include this line in your AUTOEXEC.BAT file so it will be started automatically every time you
- // start your system. Currently UNIVBE does not support the VIPER card, so you must use VPRMODE instead
- // to run in high or medium resolution. Unfortunately, the VLB version of the Viper is currently not
- // supported in high or medium resolution.
-
- #define TROUB_SPEED 318
- // ^f01 Speed
- //^f00
- // If you are experiencing slow or jerky movement in the game and/or video sequences, make sure your
- // CD is clean and that you are running off a boot disk. If this does not help, try the following:
- //
- // ^c007^f02RUN IN MSDOS MODE^c000^f00
- // If you are running under Windows 95, reduce window processor overhead by restarting your machine
- // in MSDOS mode. Note that you may need to install 16-bit sound and CD drivers if your system is not
- // normally setup to run in this mode.
- //
- // ^c007^f02ENABLE PROCESSOR CACHING^c000^f00
- // If you are using a processor upgrade chip like the CYRIX DRx2, be sure to have the CPU cache-
- // enabling software for the processor included in your AUTOEXEC.BAT file.
- //
- // ^c007^f02DISABLE DRIVE CACHING^c000^f00
- // Turn off CD-ROM caching software. It can use needed memory or lockup the program in an endless
- // logic loop should bad data be read off the CD.
- //
- // ^c007^f02CHECK CD DRIVE SPECIFICATIONS^c000^f00
- // Make sure your machine meets these minimum specifications:
- //
- // 1) a 50Mhz 486 or better CPU,
- // 2) a double-speed, MPC Level 2 CD-ROM Drive, and
- // 3) 8 Megabytes of memory.
- //
- // Use the "SysInfo" selection under the main menu to test the various components of your machine and
- // insure they meet specifications and are working properly. Beware that certain CD drives may not meet
- // MPC-Level 2 requirements, or may need a new CD driver from your CD-ROM drive manufacturer to do so.
- //
- // ^c001^f02Continued...
-
- #define TROUB_SPEED2 319
- // ^f01 Speed Continued
- //^f00
- //
- // ^c007^f02REDUCE MSCDEX BUFFER SIZE^c000^f00
- // In many cases, you can increase Mortimer's speed by minimizing MSCDEX's buffer size. Find the
- // MSCDEX line in your AUTOEXEC.BAT and change the number following the "/m:" to 4. Make sure to reboot
- // your system for the change to take effect.
- //
- // ^c007^f02SWITCHING MULTITASKING SYSTEM^c000^f00
- // You may also be able to improve CD performance on some CD drives by switching Mortimer's animation
- // system from cooperative to preemptive multitasking, particularly with drives which cause the game to
- // periodically stutter or slow down. Selecting the "Advanced Settings" item under the setup menu and
- // choose the "Task Switcher" item. Select "Preemptive" and click "OK". Leave the timer rate at 300.
- //
- // ^c007^f02ADJUSTING FRAME RATE^c000^f00
- // You can make the game run more smoothly by slowing down the frame rate from its default of 15
- // frames per second. This option appears under the "Advanced Settings" selection of the Setup Menu.
- // You may also want to slow down the frame rate to make the game easier to play.
- //
- // ^c007^f02HARDWARE-SPECIFIC ADJUSTMENTS^c000^f00
- //
- //
- //
-
- #define TROUB_MSCDEX 320
- // ^f01 Speed - Reducing MSCDEX Buffer Size
- //^f00
- //
- // To change your MSCDEX buffer size, you'll need to edit your AUTOEXEC.BAT file in a text editor.
- // Refer to the instructions below for making the changes using the DOS editor.
- //
- // 1) Make sure your boot disk is in your system's A: drive. At the LUCASARTS BOOTDISK A: prompt, type
- //
- // ^c007^f02EDIT AUTOEXEC.BAT^c000^f00
- //
- // and press the <ENTER> key. This will allow you to edit the AUTOEXEC.BAT file using the DOS editor.
- //
- // 2) Search for the MSCDEX line, moving up and down the page using the arrow keys. Change the
- // M: <M colon> value to 4, if 4 is not its current value.
- //
- // ^c007Example:
- // ^f02C:\DEV\MSCDEX.EXE /D:MSCD001 /m:4 ^c000^f00
- //
- // 3) Now exit and save the file by first holding down the <ALT> key while pressing the <F> key, and then
- // pressing <X> to exit.
- //
- // 4) Restart your system to make the changes take effect.
-
- #define TROUB_PHILIPS 321
- // ^f01 Speed - Philips CD Drives
- //^f00
- // For Philips drives using the following drivers, try modifying the driver line in your
- // boot disk's CONFIG.SYS.
- //
- //^f02^c007
- // DD250.SYS
- //^f00^c000
- // Try adjusting the memory cache. The default is /C:99. Try /C:0.
- //
- //^f02^c007
- // DD260.SYS
- //^f00^c000
- // Try adding /F:5 at the end of the driver line.
- //
-
- #define TROUB_MITSUMI 322
- // ^f01 Speed - Mitsumi CD Drives
- //^f00
- // Some Mitsumi CD-ROM drives give you the option of using a software-
- // polling driver, commonly:
- //^f02^c007
- // MTMCDAS.SYS
- //^f00^c000
- // or a DMA-polling driver, commonly:
- //^f02^c007
- // MTMCDAE.SYS
- //^f00^c000
- // If you have a Mitsumi CD-ROM drive that offers an option between these
- // drivers, try using the DMA-polling version if you are encountering poor performance while using the
- // software-polling driver.
- //
-
- #define TROUB_SPEEDJOY 325
- // ^f01 Speed - Speed-Adjustable Game Cards
- //^f00
- // If you have a speed-adjustable game card installed on your system, lower the card's speed setting.
- // Even if you are not using a joystick with the game, this may increase the performance of your other
- // peripherals, such as CD-ROM drives. Most game cards include a utility to do this. For further
- // instructions, consult your game card documentation or manufacturer directly.
-
- #define TROUB_NEC 326
- // ^f01 Speed - NEC CD Drives
- //^f00
- //
- //
- // If your are using the ASPICD.SYS driver with a triple-speed drive, make sure you have
- // version 3.10 or later.
- //
- // Contact NEC for additional information.
-
- #define TROUB_ERROR 330
- // ^f01 Error Messages
- //^f00
- // ^c007^f02CD Checksum Error^f00^c000
- //
- // This indicates that after reading the CD several times, the game was unable to find correct
- // information. This can often be due to a dirty or scratched CD. We suggest cleaning the
- // CD with a clean, slightly damp cloth and checking it for damage. Also be sure that you don't
- // have any disk-caching software (such as SMARTDrive) enabled. Running from a boot disk will insure
- // this.
- //
- // Check to make sure you have the most recent version of your CD-ROM driver software from your
- // CD-ROM drive manufacturer. Finally, you can try adjusting the game's multitasking timer rate or
- // switching the multitasker to "Cooperative" mode. See the instructions under SWITCHING MULTITASKING
- // SYSTEM in the next section of this manual for further details.
- //
- // ^c007^f02Cannot Allocate Buffer^f00^c000
- // ^c007^f02Buffer Overflow^f00^c000
- // ^c007^f02Cannot Pass into Protect Mode^f00^c000
- //
- // This is probably due to insufficient memory, possibly due to the presence of a memory manager.
- // Please review the MEMORY section of this manual.
- //
- //
- //
- //
- //
- //
- //
- // ^c001^f02Continued...
-
- #define TROUB_ERROR2 331
- // ^f01 Error Messages Continued
- //^f00
- // ^c007^f02Granular Error^f00^c000
- //
- // This occurs when the game is unable to retrieve data off the CD because either 1) the CD has
- // been removed from the CD drive, 2) there is an extended pause and the drive has spun down, or 3) the
- // CD is dirty or damaged.
- //
- // ^c007^f02Protected Mode Conflict^f00^c000
- //
- // This usually occurs when you try to launch the DOS version of the game under Windows version 3.1
- // or earlier. This will only work on Windows 95 and later releases. Try exiting windows completely
- // and running the game from DOS or making a boot disk.
- //
- // ^c007^f02DOS/4GW Fatal Error^f00^c000
- //
- // Some computers have difficulties with certain versions of the DOS extender shipped with Mortimer.
- // If you find this to be the case, install a different version following the instructions in the
- // "CRASHES/LOCKUPS" section of this manual.
-
- #define TROUB_TECH 335
- // ^f01 Technical Support
- //^f00
- // If you are having any technical difficulties with this product, please contact the technical support
- // department. If you have a technical problem, we recommend that you are sitting in front of your
- // computer when you call so that we will be able to assist you more quickly.
- //
- // It is also helpful to have a list of your machine's current hardware and software configurations.
- //
- // Please DO NOT call technical support if you have not first tried to resolve your problem
- // by making a boot disk.
- //
- // Phone - (415) 507-4545 - M-Th:8:30am - 6:00pm, F:8:30am - 5:00pm, Pacific Standard Time
- //
- // Fax - (415) 507-0300 - 24 hours
- //
- // BBS - (415) 507-0400 - 24 hours - NOT a message base. For file download ONLY.
- //
- // Mail - LucasArts Entertainment Co.
- // P.O. Box 10307
- // San Rafael, CA 94912
- //
- // ^f02^c007HINTS^f00^c000
- //
- // If you require hints or passwords for our games, please call our hintline at 1-900-740-JEDI.
- // Callers must be over the age of 18 or have their parents permission when they call.
- // Each call costs $.75 per minute.
- //
- // If you would like information about our other games or would
- // like a catalog of our products, please call us at 1-800-98LUCAS.
-
- #define TROUB_TECH2 336
- // ^f01 Online Technical Support
- //^f00
- // ^f02^c007LucasArts Entertainment BBS^c000^f00
- //
- // (415) 507-0400t8N1, ANSI 016 lines, 24 hours, 7 days a week Demos, Patches, On-line technical support
- //
- // ^f02^c007Compuserve ^c000^f00
- //
- // Send mail to 75300, 454
- // Game Publisher's Forum A
- // (Go GAMAPUB)
- //
- // ^f02^c007America Online^c000^f00
- //
- // Keyword "Lucas"
- //
- // ^f02^c007Internet E-Mail^c000^f00
- //
- // Send mail to "75300.454@COMPUSERVE.COM"
- //
- // ^f02^c007Home Page^c000^f00
- //
- // http://www.lucasarts.com/
-
- #define TROUB_CRASH2_SONY 337
- // ^f01 Crashes/Lockups - Sony CD Drives
- //^f00
- // If you have a SONY IDE CD-ROM drive, make sure you have the most recent CD-ROM drivers available.
- // Specifically, running ATAPI_CD.SYS version 2.08a has been found to be problematic, causing
- // intermittent crashes and lockups. Upgrading to version 2.17a or later seems to fix the problem.